List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.
ELEMENT | PERFORMANCE CRITERIA |
Elements describe the essential outcomes. | Performance criteria describe the performance needed to demonstrate achievement of the element. |
1. Gather and confirm client requirements | 1.1 Confirm the requirements, and the scope, of the project with the client 1.2 Gather information regarding requirements via sources of information and business processes 1.3 Analyse client requirements, to determine the project scope and the problem context or opportunity faced by the business 1.4 Document the client requirements, project’s scope, related problems, and sources of information |
2. Analyse the functional and related non-functional requirements | 2.1 Map business processes using modelling tools such as unified modelling language (UML) 2.2 Determine the opportunities for business process efficiencies 2.3 Document functional, and related non-functional, processes |
3. Analyse the feasibility of a project | 3.1 Analyse the technical feasibility of the project 3.2 Analyse the operational feasibility of the project 3.3 Determine the budget and schedule feasibility of the project 3.4 Examine how the project will fit within the organisation |
4. Develop high-level system solutions | 4.1 Develop and document feasible solutions for client requirements 4.2 Explore and document the feasibility of each solution 4.3 Examine alternatives against project constraints 4.4 Document assumptions, dependencies and required resources 4.5 Produce a project risk analysis 4.6 Document future requirements |
5. Prepare and publish the software-requirements documentation | 5.1 Develop the software-requirements document 5.2 Submit the software-requirements report to the appropriate person for project approval |
Evidence of the ability to:
Analyse client requirements to create a software requirements document, including:
gathering, confirming and documenting client requirements
analysing functional and related non-functional requirements, and project feasibility
developing high-level system solutions
submitting documents for approval.
Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.
To complete the unit requirements safely and effectively, the individual must:
identify the client business domain
describe content features, such as clarity and readability
summarise the system's current functions
explain document design and usability
explain the functions and features, of templates and style guides
summarise instructional design principles
describe the role of stakeholders and the degree of stakeholder involvement
explain two or more current industry systems development methodologies.
Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:
documentation regarding client and functionality requirements
word processing software
modelling software currently used in industry.
Assessors must satisfy NVR/AQTF assessor requirements.